System and Method to Account for I/O Read Latency in Processor Caching Algorithms

ABSTRACT

A processor includes a cache memory and a cache controller. The cache controller fetches first data from a first location of an information handling system, stores the first data to a first cache line of a plurality of cache lines, determines first proximity information for the first data based upon the first location, stores the first proximity information in a first proximity tag associated with the first cache line, and evicts the first cache line from the cache based upon the first proximity tag.

FIELD OF THE DISCLOSURE

This disclosure generally relates to information handling systems, andmore particularly relates to accounting for I/O read latency inprocessor caching algorithms.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, and/or communicatesinformation or data for business, personal, or other purposes. Becausetechnology and information handling needs and requirements may varybetween different applications, information handling systems may alsovary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information may be processed, stored, orcommunicated. The variations in information handling systems allow forinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing,reservations, enterprise data storage, or global communications. Inaddition, information handling systems may include a variety of hardwareand software resources that may be configured to process, store, andcommunicate information and may include one or more computer systems,data storage systems, and networking systems.

SUMMARY

A processor may include a cache memory and a cache controller. The cachememory may include a plurality of cache lines, each cache line includinga proximity tag. The cache controller may fetch first data from a firstlocation of an information handling system, store the first data to afirst cache line of the plurality of cache lines, determine firstproximity information for the first data based upon the first location,store the first proximity information in a first proximity tagassociated with the first cache line, and evict the first cache linefrom the cache based upon the first proximity tag.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures have not necessarily been drawn toscale. For example, the dimensions of some of the elements areexaggerated relative to other elements. Embodiments incorporatingteachings of the present disclosure are shown and described with respectto the drawings presented herein, in which:

FIG. 1 is a block diagram illustrating a generalized informationhandling system according to an embodiment of the present disclosure;

FIG. 2 is a block diagram of a processor according to an embodiment ofthe present disclosure;

FIG. 3 is a block diagram of an information handling system according toan embodiment of the present disclosure;

FIG. 4 is a block diagram of the information handling system of FIG. 3that illustrates a method for accounting for I/O read latency inprocessor caching algorithms according to an embodiment of the presentdisclosure; and

FIG. 5 is a flowchart illustrating a method for accounting for I/O readlatency in processor caching algorithms according to an embodiment ofthe present disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The followingdiscussion will focus on specific implementations and embodiments of theteachings. This focus is provided to assist in describing the teachings,and should not be interpreted as a limitation on the scope orapplicability of the teachings. However, other teachings can certainlybe used in this application. The teachings can also be used in otherapplications, and with several different types of architectures, such asdistributed computing architectures, client/server architectures, ormiddleware server architectures and associated resources.

FIG. 1 illustrates a generalized embodiment of an information handlingsystem 100. For purpose of this disclosure information handling system100 can be configured to provide the features and to perform thefunctions of the information handling system as described herein.Information handling system 100 can include any instrumentality oraggregate of instrumentalities operable to compute, classify, process,transmit, receive, retrieve, originate, switch, store, display,manifest, detect, record, reproduce, handle, or utilize any form ofinformation, intelligence, or data for business, scientific, control,entertainment, or other purposes. For example, information handlingsystem 100 can be a personal computer, a laptop computer, a smart phone,a tablet device or other consumer electronic device, a network server, anetwork storage device, a switch router or other network communicationdevice, or any other suitable device and may vary in size, shape,performance, functionality, and price. Further, information handlingsystem 100 can include processing resources for executingmachine-executable code, such as a central processing unit (CPU), aprogrammable logic array (PLA), an embedded device such as aSystem-on-a-Chip (SoC), or other control logic hardware. Informationhandling system 100 can also include one or more computer-readablemedium for storing machine-executable code, such as software or data.Additional components of information handling system 100 can include oneor more storage devices that can store machine-executable code, one ormore communications ports for communicating with external devices, andvarious input and output (I/O) devices, such as a keyboard, a mouse, anda video display. Information handling system 100 can also include one ormore buses operable to transmit information between the various hardwarecomponents.

Information handling system 100 can include devices or modules thatembody one or more of the devices or modules described below, andoperates to perform one or more of the methods described below.Information handling system 100 includes a processors 102 and 104, achipset 110, a memory 120, a graphics interface 130, a basic input andoutput system/extensible firmware interface (BIOS/EFI) module 140, adisk controller 150, a hard disk drive (HDD) 154, an optical disk drive(ODD) 156, a disk emulator 160 connected to an external solid statedrive (SSD) 162, an input/output (I/O) interface 170, one or more add-onresources 174, a trusted platform module (TPM) 176, a network interface180, a management block 190, and a power supply 195. Processors 102 and104, chipset 110, memory 120, graphics interface 130, BIOS/EFI module140, disk controller 150, HDD 154, ODD 156, disk emulator 160, SSD 162,I/O interface 170, add-on resources 174, TPM 176, and network interface180 operate together to provide a host environment of informationhandling system 100 that operates to provide the data processingfunctionality of the information handling system. The host environmentoperates to execute machine-executable code, including platform BIOS/EFIcode, device firmware, operating system code, applications, programs,and the like, to perform the data processing tasks associated withinformation handling system 100.

In the host environment, processor 102 is connected to chipset 110 viaprocessor interface 106, and processor 104 is connected to the chipsetvia processor interface 108. Memory 120 is connected to chipset 110 viaa memory bus 122. Graphics interface 130 is connected to chipset 110 viaa graphics interface 132, and provides a video display output 136 to avideo display 134. In a particular embodiment, information handlingsystem 100 includes separate memories that are dedicated to each ofprocessors 102 and 104 via separate memory interfaces. An example ofmemory 120 includes random access memory (RAM) such as static RAM(SRAM), dynamic RAM (DRAM), non-volatile RAM (NV-RAM), or the like, readonly memory (ROM), another type of memory, or a combination thereof.

BIOS/EFI module 140, disk controller 150, and I/O interface 170 areconnected to chipset 110 via an I/O channel 112. An example of I/Ochannel 112 includes a Peripheral Component Interconnect (PCI)interface, a PCI-Extended (PCI-X) interface, a high speed PCI-Express(PCIe) interface, another industry standard or proprietary communicationinterface, or a combination thereof. Chipset 110 can also include one ormore other I/O interfaces, including an Industry Standard Architecture(ISA) interface, a Small Computer Serial Interface (SCSI) interface, anInter-Integrated Circuit (I²C) interface, a System Packet Interface(SPI), a Universal Serial Bus (USB), another interface, or a combinationthereof. BIOS/EFI module 140 includes BIOS/EFI code operable to detectresources within information handling system 100, to provide drivers forthe resources, initialize the resources, and access the resources.BIOS/EFI module 140 includes code that operates to detect resourceswithin information handling system 100, to provide drivers for theresources, to initialize the resources, and to access the resources.

Disk controller 150 includes a disk interface 152 that connects the diskcontroller to HDD 154, to ODD 156, and to disk emulator 160. An exampleof disk interface 152 includes an Integrated Drive Electronics (IDE)interface, an Advanced Technology Attachment (ATA) such as a parallelATA (PATA) interface or a serial ATA (SATA) interface, a SCSI interface,a USB interface, a proprietary interface, or a combination thereof. Diskemulator 160 permits SSD 164 to be connected to information handlingsystem 100 via an external interface 162. An example of externalinterface 162 includes a USB interface, an IEEE 1394 (Firewire)interface, a proprietary interface, or a combination thereof.Alternatively, solid-state drive 164 can be disposed within informationhandling system 100.

I/O interface 170 includes a peripheral interface 172 that connects theI/O interface to add-on resource 174, to TPM 176, and to networkinterface 180. Peripheral interface 172 can be the same type ofinterface as I/O channel 112, or can be a different type of interface.As such, I/O interface 170 extends the capacity of I/O channel 112 whenperipheral interface 172 and the I/O channel are of the same type, andthe I/O interface translates information from a format suitable to theI/O channel to a format suitable to the peripheral channel 172 when theyare of a different type. Add-on resource 174 can include a data storagesystem, an additional graphics interface, a network interface card(NIC), a sound/video processing card, another add-on resource, or acombination thereof. Add-on resource 174 can be on a main circuit board,on separate circuit board or add-in card disposed within informationhandling system 100, a device that is external to the informationhandling system, or a combination thereof.

Network interface 180 represents a NIC disposed within informationhandling system 100, on a main circuit board of the information handlingsystem, integrated onto another component such as chipset 110, inanother suitable location, or a combination thereof. Network interfacedevice 180 includes network channels 182 and 184 that provide interfacesto devices that are external to information handling system 100. In aparticular embodiment, network channels 182 and 184 are of a differenttype than peripheral channel 172 and network interface 180 translatesinformation from a format suitable to the peripheral channel to a formatsuitable to external devices. An example of network channels 182 and 184includes InfiniBand channels, Fibre Channel channels, Gigabit Ethernetchannels, proprietary channel architectures, or a combination thereof.Network channels 182 and 184 can be connected to external networkresources (not illustrated). The network resource can include anotherinformation handling system, a data storage system, another network, agrid management system, another suitable resource, or a combinationthereof.

Management block 190 represents one or more processing devices, such asa dedicated baseboard management controller (BMC) System-on-a-Chip (SoC)device, one or more associated memory devices, one or more networkinterface devices, a complex programmable logic device (CPLD), and thelike, that operate together to provide the management environment forinformation handling system 100. In particular, management block 190 isconnected to various components of the host environment via variousinternal communication interfaces, such as a Low Pin Count (LPC)interface, an Inter-Integrated-Circuit (I2C) interface, a PCIeinterface, or the like, to provide an out-of-band (00B) mechanism toretrieve information related to the operation of the host environment,to provide BIOS/UEFI or system firmware updates, to managenon-processing components of information handling system 100, such assystem cooling fans and power supplies. Management block 190 can includea network connection to an external management system, and themanagement block can communicate with the management system to reportstatus information for information handling system 100, to receiveBIOS/UEFI or system firmware updates, or to perform other task formanaging and controlling the operation of information handling system100. Management block 190 can operate off of a separate power plane fromthe components of the host environment so that the management blockreceives power to manage information handling system 100 when theinformation handling system is otherwise shut down. An example ofmanagement block 190 may include a commercially available BMC productthat operates in accordance with an Intelligent Platform ManagementInitiative (IPMI) specification, such as a Integrated Dell Remote AccessController (iDRAC), or the like. Management block 190 may furtherinclude associated memory devices, logic devices, security devices, orthe like, as needed or desired.

Power supply 195 represents one or more devices for power distributionto the components of information handling system 100. In particular,power supply 195 can include a main power supply that receives powerfrom an input power source, such as a wall power outlet, a power strip,a battery, or another power source, as needed or desired. Here, powersource 195 operates to convert the power at a first voltage level fromthe input power source to one or more power rails that are utilized bythe components of information handling system. Power supply 195 can alsoinclude one or more voltage regulators (VRs) that each receive powerfrom the main power supply and that operate to convert the input voltageto an output voltage that is used by one or more components ofinformation handling system. For example, a VR can be provided for eachof processors 102 and 104, and another VR can be provided for memory120. Power supply 195 can be configured to provide a first power planethat provides power to the host environment, and to provide a secondpower plane that provides power to the management environment.

FIG. 2 illustrates an embodiment of a processor die 200. In a particularembodiment, processor die 200 represents a portion of a multi-chipprocessor (MCP) that includes two (2) or more processor dies similar toprocessor die 200. For example, a MCP may include eight (8) processordie similar to processor die 200. In keeping with this embodiment, theMCP represents a portion of an information handling system similar toinformation handling system 100. The information handling system mayinclude two (2) or more MCPs, where each MCP includes multiple processordies similar to processor die 200. For example, an information handlingsystem may include two (2) MCPs that each include eight (8) processordies similar to processor die 200. Such an information handling systemis shown in FIGS. 3 and 4, as described further, below. In anotherembodiment, processor die 200 represents a portion of an informationhandling system similar to information handling system 100. Theinformation handling system of this embodiment may include one or moreprocessor dies similar to processor die 200.

Processor die 200 includes processor core 212, a cache controller 214,an eight-way set associative cache memory 216 and an associatedreplacement tag RAM 218, a replacement tag priority register 220, alocation information register 221, an I/O controller 222, a memoryinterface 224, a die-to-die interface 226, an inter-socket interface228, and an I/O interface 230. Processor core 212 represents one or moreprocessor nodes that are configured to execute machine executable code.In a particular embodiment, processor core 212 represents eight (8)individual processor nodes. Here, it will be understood that eachprocessor node of processor core 212 may include primary code and datacache structures that store recently used code and data and that arededicated to the use of the associated processor node. However, withrespect to the present disclosure, all processor nodes of processor core212 will be understood to share caching operations via cache controller214, cache 216, and tag RAM 218 on the level of processor die 200, asdescribed herein. As such, the details of caching with respect to theindividual processor nodes of processor core 212 are known in the artand are beyond the scope of the present disclosure, and such detailswill only be discussed as needed to illuminate the present disclosure.

Cache controller 214 represents logic of processor die 200 that controlsthe transfer of information between core 212, cache 216, and the variousI/O devices that are connected to the processor die. When core 212accesses a particular memory address in the main memory of theinformation handling system, cache controller 214 determines whether ornot the information associated with the memory address is stored incache 216. If so, cache controller 214 provides the information to core212. If the information associated with the memory address is not storedin cache 216, cache controller 214 provides the memory address to I/Ocontroller 222 to fetch the information from the memory address. I/Ocontroller 222 determines whether the memory address is associated withmemory devices that are connected to memory interface 224, with memorydevices that are connected to other processor die, or with I/O devicesthat are connected to I/O interface 230. The interface 224, 226, 228, or230 associated with the memory address then issues transactions to fetchthe information from the device associated with the memory address, andprovides the information back through I/O controller 222 to cachecontroller 214. When cache controller 214 receives the informationassociated with the memory address access from core 212, the cachecontroller provides the information to the core, and stores theinformation to cache 216. It will be understood that data caching inprocessor die 200 may involve determinations as to the cacheability ofthe information from various memory locations, and that cache controller214 may participate in such determinations. However, for the purpose ofthis disclosure, all information handled by processor die 200 will beunderstood to be from cacheable memory addresses. Note that theparticular configuration of processor die 200 is illustrative of agenerally implemented processor die architecture, and that otherprocessor die architectures may be implemented without violating theteachings of the present disclosure. For example, in a particularprocessor die, an I/O controller may be disaggregated from a separatememory controller subsystem. Other details may be implemented as neededor desired in a particular processor die.

Before the information fetched from a memory address of the main memorycan be stored in cache 216, cache controller 214 must determine if thereis an empty cache line associated with that memory address in any of theeight (8) ways of the cache. If so, the information is stored in theempty cache line. If not, then the cache line associated with thatmemory address in one of the eight (8) ways must be evicted from thecache in order to make room for the newly fetched information. It willbe understood that any cache line eviction will need to be performed bycache controller 214 in accordance with a particular cache coherencyprotocol, such as a Modified, Exclusive, Shared, Invalid (MESI) protocolor another cache coherency protocol, as needed or desired. However, thedetails of cache coherency protocols are known in the art and are beyondthe scope of the present disclosure, and such details will only bediscussed as needed to illuminate the present disclosure.

Cache controller 214 controls the eviction of existing informationstored in cache 216 with the newly fetched information based upon ausage eviction policy and a location eviction policy. An example of ausage eviction policy can include a first-in-first-out (FIFO) policy, alast-in-first-out (LIFO) policy, a least recently used (LRU) policy, atime-aware LRU policy, a most recently used (MRU) policy, a leastfrequently used (LFU) policy, a pseudo-LRU policy, a random replacementpolicy, a segmented-LRU policy, or another usage eviction policy, asneeded or desired. In a FIFO policy, cache controller 214 evicts thecache line from the way that was stored first, regardless of how oftenor how many times the cache line has been accessed before. In a LRUpolicy, cache controller 214 evicts the cache line from the way that wasaccessed least recently. Here, replacement tag RAM 218 includes three(3) age bits that permit the tracking of least recently used cache line.For example, when a particular cache line is accessed, the age bitsassociated with that cache line in the associated way can be clearedsuch that the three age bits all store binary zeros (000b). Then, eachthe age bits of the corresponding cache lines in each of the other seven(7) ways are incremented by one (1), unless the cache line is accessedin successive accesses, in which case the age bits in the other seven(7) ways remain unchanged. Then, when a cache line is to be evicted, thecache line whose age bits all store binary ones (111b), will be selectedto evicted. In a LFU policy, cache controller 214 evicts the cache linefrom the way that was accessed least often. Here, replacement tag RAM218 includes access bits that count the number of accesses for eachcache line in each way. For example, a first cache line may have beenaccessed three (3) times, a second cache line may have been accessedfive (five) times, and a third cache line may have been accessed eight(8) times. Here, when a cache line needs to be evicted, then cachecontroller 214 will evict the first cache line, even if it is the mostrecently used cache line.

In implementing the location eviction policy, cache controller 214operates to determine a proximity of the source of the information in aparticular cache line to processor die 200. Here, for example,replacement tag RAM 218 includes three (3) location bits that permit thesource location of the information in each cache line. Other numbers oflocation bits may be utilized as needed or desired. Here further,information from more remote locations from processor die 200 will beretained in cache 216, because fetching such information results inlonger delays. On the other hand, information from more proximatelocations to processor die 200 will be evicted from cache 216, becausefetching such information results in shorter delays. For example,information from a memory device connected to memory interface 224 maybe deemed to be most proximate to processor die 200 and so can bequickly fetched, while information from an I/O device connected toanother processor die may be deemed to be least proximate to theprocessor die, and would therefore incur a great penalty. As such, cachecontroller 214 operates to preferentially retain data from more remotelocations and to preferentially evict data from more proximatelocations. The details of the location eviction policy will be furtherdescribe with respect to FIGS. 3 and 4, below. FIG. 2 furtherillustrates one line 219 of replacement tag RAM 218, and a detailedillustration of replacement tag priority register 220. Both replacementtag RAM 218 and replacement tag priority register 220, and also locationinformation register 221, will be fully described below.

FIG. 3 illustrates an information handling system 300 similar toinformation handling system 100. The architecture of informationhandling system 300 includes a multi-chip processor (MCP) 305, a MCP345, and a system Basic Input/Output System (BIOS)/Universal ExtensibleFirmware Interface (UEFI) 390. MCP 305 includes four processor die 310,320, 330, and 340, similar to processor die 200. Processor dies 310,320, 330, and 340 are connected together via point-to-point data linksestablished between die-to-die interfaces similar to die-to-dieinterfaces 226. As such, processor die 310 is connected to processor die320 via a first point-to-point data link, to processor die 330 via asecond point-to-point data link, and to processor die 340 via a thirdpoint-to-point data link. Similarly, processor die 320 is connected toprocessor die 330 via a fourth point-to-point data link and to processordie 330 via a fifth point-to-point data link, and finally, processor die330 is connected to processor die 340 via a sixth point-to-point datalink. An example of the point-to-point data links include a coherentfabric between processor dies 310, 320, 330, and 340, such as a GlobalMemory Interconnect (GMI) fabric.

Similarly, MCP 345 includes four processor die 350, 360, 370, and 380similar to processor die 200. Processor dies 350, 360, 370, and 380 areconnected together via point-to-point data links similarly to MCP 305via seventh, eighth, ninth, tenth, eleventh, and twelfth point-to-pointdata links. The point-to-point data links are established betweendie-to-die interfaces similar to die-to-die interfaces 226. Further,processor die 310 is connected to processor die 350 via a thirteenthpoint-to-point data link, processor die 320 is connected to processordie 360 via a fourteenth point-to-point data link, processor die 330 isconnected to processor die 370 via a fifteenth point-to-point data link,and processor die 340 is connected to processor die 380 via a sixteenthpoint-to-point data link. The point-to-point data links betweenprocessor dies 310 and 350, between processor dies 320 and 360, betweenprocessor dies 330 and 370, and between processor dies 340 and 380 areestablished between inter-socket interfaces similar to inter-socketinterface 228. An example of the point-to-point data links betweenprocessor dies 310, 320, 330, 340, 350, 360, 370, and 380 include aGraphics Output Protocol (GOP) fabric. Each of processor die 310, 320,330, 340, 350, 360, 370, and 380 includes eight processor cores. Eachcore can process up to two threads. Thus information handling system 300can process up to 128 threads simultaneously. Processor dies 310, 320,330, 340, 350, 360, 370, and 380 each include a respective cachecontroller 311, 321, 331, 341, 351, 361, 371, and 381. Cache controllers311, 321, 331, 341, 351, 361, 371, and 381 are similar to cachecontroller 214.

Information handling system 300 provides a Non-Uniform Memory Access(NUMA) architecture, where each of processor dies 310, 320, 530, 340,350, 360, 370, and 380 support one or more memory channels via memoryinterfaces similar to memory interface 224. As such, informationhandling system 300 is shown with processor die 310 connected to a DualIn-Line Memory Module (DIMM) 312, with processor die 320 connected toDIMM 322, with processor die 330 connected to DIMM 332, with processordie 340 connected to DIMM 342, with processor die 350 connected to DIMM352, with processor die 360 connected to DIMM 362, with processor die370 connected to DIMM 372, and with processor die 380 connected to DIMM382. An example of memory channels and associated DIMMs 312, 322, 332,342, 352, 362, 372, and 382 includes memory devices in accordance with aDouble Data Rate (DDR) DIMM standard, such as a DDR-4 standard, a DDR-5standard, or another DDR standard. DIMMs 312, 322, 332, 342, 352, 362,372, and 382 do not necessarily represent a full population of DIMMmodules. For example, each of DIMMs 312, 322, 332, 342, 352, 362, 372,and 382 may, in fact represent two or four DIMM sockets per memorychannel, each of which may or may not actually be populated with a DIMMdevice in a particular configuration of information handling system 300.For example, information handling system 300 may be configured toprovide an optimal level of system performance at a minimum cost, and somy be configured with only one DIMM module per memory channel, leaving1-3 DIMM sockets unpopulated and available for future expansion.

Each of processor die 310, 320, 330, 340, 350, 360, 370, and 380 furthersupports one 16 lane (×16) serial data interface via I/O interfacessimilar to I/O interface 230. The ×16 serial data interfaces are highlyconfigurable, supporting several different interface configurationprotocols and data rates, as needed or desired. For example, the ×16serial data interfaces may each be configured in accordance with variousPCIe standards, and groups of serial data lanes can be logicallyconfigured as ×16 PCIe serial data interfaces, as ×8 serial datainterfaces, as ×4 serial data interfaces, as ×2 serial data interfaces,or as ×1 serial data interfaces, as needed or desired. Limitations onpermissible configurations are known in the art, as may be dictated byBIOS considerations, PCIe specification considerations, or otherconsiderations, and will not be further discussed herein. Some or all ofthe serial data lanes of the ×16 serial data interfaces may also beconfigured in accordance with various Serial-ATA (SATA), SATA-Express,or Ethernet port standards, as needed or desired, and as supported bythe various architecture standards for information handling system 300.As illustrated, information handling system 300 is shown with processordie 310 connected to an I/O device 314, with processor die 320 connectedto an I/O device 324, with processor die 330 connected to an I/O device334, with processor die 340 connected to an I/O device 344, withprocessor die 350 connected to an I/O device 354, with processor die 360connected to an I/O device 364, with processor die 370 connected to anI/O device 374, and with processor die 380 connected to an I/O device384. Note that other I/O device configurations may be provided withoutviolating the teachings of the present disclosure.

Information handling system 300 operates to provide a measure of theproximity between cache controllers 311, 321, 331, 341, 351, 361, 371,and 381 and each of DIMMs 312, 322, 332, 342, 352, 362, 372, and 382,and between the cache controllers and each of I/O devices 314, 324, 334,344, 354, 364, 374, and 384. In the illustrated embodiment, BIOS/UEFI390 is configured with a location table 302 that correlates a proximityof each of cache controllers 311, 321, 331, 341, 351, 361, 371, and 381to each of DIMMs 312, 322, 332, 342, 352, 362, 372, and 382, and to eachof I/O devices 314, 324, 334, 344, 354, 364, 374, and 384, by ascribingan indication of proximity, or proximity number, to each correlation. Inthe illustrated embodiment, for reasons which will become clear wherereplacement tag RAM 219 and replacement tag priority register 220 aredescribed more fully, below, DIMMs and I/O devices that are moreproximate to a particular cache controller are ascribed a higher number,while DIMMs and I/O devices that are more distant to that cachecontroller are ascribed a lower number. For example, considering cachecontroller 311, shown in location table 301 as “M1/CC1,” DIMM 312 isconnected directly to processor die 310, and hence is ascribed a highestproximity number of 7. Further, I/O device 314 is directly connected toprocessor die 310, but, upon an assumption that I/O devices are slowerthan DIMMs, is ascribed a proximity number of 6. Next, DIMMs 322, 332,and 342, being connected to the other processor die 320, 330, and 340 ofMCP 305, will necessitate transactions that hop between processor dies,and so are ascribed a lower proximity number of 5. Similarly, I/Odevices 324, 334, and 344, being connected to the other processor die320, 330, and 340 of MCP 305, will necessitate transactions that hopbetween processor dies, but are again assumed to slower than theassociated DIMMs, and so are ascribed a yet lower proximity number of 4.In a particular embodiment, location table 302 is configured based upona memory map of a main memory space of information handling system 300,and DIMMs 312, 322, 332, 342, 352, 362, 372, and 382, and I/O devices314, 324, 334, 344, 354, 364, 374, and 384 are each associated with arange of memory in the memory map.

A further assumption is made that transactions between cache controllerson MCP 305 and the DIMMs and I/O devices connected to MCP 345 are slowerthan transactions the cache controllers on MCP 305 and the DIMMs and I/Odevices connected to MCP 305. Thus, transactions between cachecontroller 311 and DIMM 352 will necessitate a hop to processor die 345,and so is ascribed a lower proximity number of 3, while I/O device 354will be ascribed a proximity number of 2. Finally, transactions betweencache controller 311 and DIMMs 362, 372, and 382, and between the cachecontroller and I/O devices 364, 374, and 384 will necessitate a furtherhop between processor die 350 and the associated processor die 360, 370,and 380, the DIMMS are ascribed a proximity number of 1, and the I/Odevices are ascribed a proximity number of 0. Note that as illustratedthe proximity numbers can be encoded using three bits, where a proximitynumber of 0 can be encoded as (000b) and a proximity number of 7 can beencoded as (111b). However, different number of bits may be utilized asneeded or desired. For example, no difference in latency may be assumedbetween DIMM transactions and I/O transactions on a particular processordie, and so fewer bits may be needed to encode the proximity numbers. Inanother example, the illustrated I/O devices may each represent one ormore devices that are associated with the I/O interfaces, and differentlatencies may be ascribed to the various I/O devices, therebynecessitating a greater number of bits to encode the proximity numbers.In this embodiment, location table 302 can be provided based upon apre-determined understanding of the architecture of information handlingsystem 300, and so the location table can be provided as a fixed entitywithin BIOS/UEFI 390.

Note that location table 302 endeavors to ascribe a number to the timesneeded for a particular cache controller to access the various DIMMs andI/O devices, and so this location table is based upon the variousassumptions described above. However, the skilled artisan willunderstand that, in a real world embodiment, such assumptions may nothold true. For example, it may be the case that all DIMMs that areconnected to a particular MCP have an approximately equal latency to allcache controllers on that MCP, and so all of the DIMMs on an MCP can beascribed a same proximity number to all of the cache controllers on thatsame MCP. In another example, the proximity numbers ascribed to thevarious I/O devices may change due to the nature of the various I/Odevices. For example, where one I/O device represents a firmware ROM ona main board of information handling system 300, and another I/O devicerepresents a storage controller configured to access a storage array ofthe information handling system, the proximity numbers may be differentbetween the I/O devices to reflect the different latencies. In anotherexample, the memory can be included in a disaggregated informationhandling system or other appliance, and can be accessed over acommunication network through the I/O devices. As such, a more detailedanalysis of the architecture of information handling system 300 would beunderstood by the skilled artisan to yield more accurate information inproviding a location table for an information handling system.

In another embodiment, a location table similar to location table 302 iscreated during a system boot process of information handling system.Here, BIOS/UEFI 390 operates to time transactions between each of cachecontrollers 311, 321, 331, 341, 351, 361, 371, and 381 and each of DIMMs312, 322, 332, 342, 352, 362, 372, and 382, and between each of thecache controllers and each of I/O devices 314, 324, 334, 344, 354, 364,374, and 384. For example, BIOS/UEFI 390 can operate to compare atimestamp for when a transaction is issued to a timestamp for when thetransaction response is received. Then, having actual timinginformation, BIOS/UEFI 390 operates to populate location table 302. In afirst case, BIOS/UEFI 390 loads the actual times of each transactioninto location table 302. For example, a binary count of the time foreach transaction can be loaded into location table 302, or, if a numberof bits needed to capture all of the transactions' times is greater thanthe number of bits available for each correlation, than BIOS/UEFI 390can truncate a number of the least significant bits of the times toprovide approximations of the actual times to populate the locationtable. Here, location table 302 will provide information as to therelative duration of each transaction, and can more accurately determinea tradeoff between a usage eviction policy and a location evictionpolicy, as described further, below.

In a second case, BIOS/UEFI 390 loads a ranking similar to the rankingshow in the illustrated example of location table 302. However, here,the ranking is based upon actual time measurements for the varioustransactions, rather than on a strict architectural analysis ofinformation handling system 300. Here, for example, the timing analysismay reveal that a latency between cache controller 311 and I/O device334 is as long as the latency between the cache controller and DIMM 352connected to processor die 350, and so, BIOS/UEFI 390 can store aproximity number of 3 in the associated correlation between the cachecontroller and the I/O device, instead of storing the proximity numberof 4, to show that the latency is approximately the same as fortransactions with the DIMM. In either case, after BIOS/UEFI 390populates location table 302, the BIOS/UEFI provides the informationfrom each row of the location table to the associated processor die. Therow information for each cache controller is then stored by therespective processor dies to a location information register similar tolocation information register 221, for use by each cache controller inimplementing its location eviction policy.

In another embodiment, each cache controller operates to timetransactions between itself and each of DIMMs 312, 322, 332, 342, 352,362, 372, and 382, and between itself and each of I/O devices 314, 324,334, 344, 354, 364, 374, and 384. For example, the cache controllers canoperate to compare a timestamp for when a transaction is issued to atimestamp for when the transaction response is received. Then each cachecontroller populates its own location information register. As notedabove with the BIOS/UEFI embodiment, each cache controller can populateits location information register with the actual times of eachtransactions, or with a ranking of the correlations, as needed ordesired.

Returning to FIG. 2, replacement tag RAM 218 includes a portion ofreplacement tag RAM 219 for each cache line in each way of cache 216.Replacement tag RAM 219 includes six bit locations. In the illustratedembodiment, because cache 216 is an eight-way cache, three bits areutilized for encoding a usage of the contents of each cache line. In thefollowing discussion, the usage eviction policy will be assumed to be aLRU policy, but other usage-based eviction policies may be utilized bycache controller 214, as needed or desired. As such, a bit combination(000b) encodes a most recently used cache line, and a bit combination(111b) encodes the least recently used cache line. The other three bitsof replacement tag RAM 219 are utilized for encoding a locationassociated with the contents of each cache line. For example, assumingthat processor die 200 is associated with processor die 310 ofinformation handling system 300, then the contents of a cache line thatwas fetched from an address location associated with DIMM 312 will beascribed a three-bit combination of (111b), based upon the value of theproximity number (7) in location table 302, and the contents of a cacheline that was fetched from an address location associated with any ofI/O devices 364, 374, or 384 will be ascribed a three-bit combination of(000b), based upon the value of the proximity number (0) in the locationtable.

In a particular embodiment, the location eviction policy is given ahigher priority in eviction decisions than the usage eviction policy byascribing the three-bits of the proximity value to bit locations 5-3 ofreplacement tag RAM 219, and ascribing the three-bits of the LRU valueto bit locations 2-0 of the replacement tag RAM. Then, when a cache lineis to be evicted, cache controller 214 compares the values stored inreplacement tag RAM 218 for each of the eight (8) cache lines, andevicts the cache line with the highest combined value of the six-bits ofthe replacement tag RAM. For example, if all eight cache lines are froma location with a same proximity number, then the least recently usedcache line will be evicted. However, where the cache lines come fromlocations with different proximity numbers, then the cache line with thehighest proximity number, that is, the cache line from the mostproximate location, will be evicted. Where there are two or more cachelines that come from locations with the same, highest, proximity number,then the LRU bits will break the tie, and the cache line that is theleast recently used of the two or more cache lines will be evicted. Notethat, if the location eviction policy is given a lower priority ineviction decisions than the usage eviction policy by ascribing thethree-bits of the proximity value to bit locations 2-0 of replacementtag RAM 219, and ascribing the three-bits of the LRU value to bitlocations 5-3 of the replacement tag RAM, then processor die 200 willimplement a strict usage eviction policy.

An example algorithm for determining which cache line to evict providesthat the most significant bits of each of the eight (8) replacement tagRAMs 219 are compared. If one most significant bit stores a 1 and all ofthe rest store a 0, then the cache line that stores the 1 is evicted. Iftwo or more most significant bits store a 1, then the next significantbits of those cache lines are compared, and the process repeats until asingle cache line is identified for eviction. If all of the mostsignificant bits store a 0, then the next most significant bits of allcache lines are compared and the process repeats until a single cacheline is identified for eviction. This is why, as described above withrespect to location table 302, the more closely proximate devices areascribed a higher proximity number, and the more remote devices areascribed a lower proximity number. The skilled artisan will understandthat the senses of the proximity numbers and the LRU bits can beinverted, and the above algorithm can likewise be inverted to search forthe cache line with the lowest combined value of the six-bit ofreplacement tag RAM 219. Here, the sense of the proximity numbers andthe LRU bits can be selected as needed or desired.

Replacement tag priority register 220 operates to select the order ofpriority for the proximity numbers and the LRU bits. As such,replacement tag priority register 220 is shown as including six (6)fields of 3-bits each. Each field is configured to assign a specifiedbit of either the proximity number or the LRU bits to the associated bitof replacement tag RAM 218. For example, proximity numbers and LRU bitscan be encoded as shown in Table 1, below.

TABLE 1 Eviction Bit Encoding Code 111 110 101 100 011 010 001 000 BitPROX₂ PROX₁ PROX₀ Invalid LRU₂ LRU₁ LRU₀ Invalid

Here, by storing the string “111/110/101/011/010/001” to replacement tagpriority register 220, the above scheme where the location evictionpolicy is given a higher priority in eviction decisions than the usageeviction policy, because the six (6) bits of replacement tag RAM 218will be ordered as PROX₂, PROX₁, PROX₀, LRU₂, LRU₁, LRU₀. In anotherembodiment, the proximity numbers and LRU bits can be interleaved toorder the six (6) bits of replacement tag RAM 218 as PROX₂, LRU₂, PROX₁,LRU₁, PROX₀, LRU₀, by storing the string 111/011/110/010/101/001 toreplacement tag priority register 220. Other eviction policyprioritization schemes can hereby be utilized by cache controller 214,as needed or desired.

FIG. 4 illustrates an example of accounting for I/O read latency in thecaching algorithms for information handling system 300. Here, DIMM 312is illustrated as storing code to run a process P1, and a shared objectSO1. Further, DIMM 372 is illustrated as storing code to run a processP2. Processor die 380 is shown as having fetched the code to run processP2 and stored the code in the cache of the processor die. Processor die380 is further shown as having fetched the shared object SO1 and storedthe shared object in the cache of the processor die. In processor die380, when new information is fetched, an eviction decision is neededbetween the process P2 code and the shared object SO1. Assuming thatprocessor die 380 has implemented a scheme where the location evictionpolicy is given a higher priority in eviction decisions than the usageeviction policy, then the process code P2 will be evicted, even if theshared object SO1 is the least recently used information. Note that inan information handling system such as information handling system 300,each processor die 310, 320, 330, 340, 350, 360, 370, and 380 canprioritize between a usage eviction policy and a location evictionpolicy by programming its own replacement tag priority register asneeded or desired, and all processor die do not need to implement thesame prioritization scheme.

FIG. 5 illustrates a method of accounting for I/O read latency inprocessor caching algorithms, starting at block 502. For each processorcore in an information handling system, the latencies between theprocessor die and each DIMM and I/O device is determined in block 504.For example, a BIOS/UEFI can be provided with a location table basedupon the architecture of the information handling system, or theBIOS/UEFI or a cache controller of the processor die can determine thelatencies between the processor die and each DIMM and I/O device of theinformation handling system. The latencies can be stored in a locationtable similar to latency table 302. The latency information is stored tothe processor die in block 506. For example, the information from thelocation table can be provided to the processor die, and the processordie can store the latency information to a latency information register.The information from the location table can be stored in locationinformation register similar to location information register 221. Areplacement tag priority register is programmed in the processor die toestablish a prioritization between usage eviction policies and alocation eviction policy in block 508, and the method ends in block 510.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover any andall such modifications, enhancements, and other embodiments that fallwithin the scope of the present invention. Thus, to the maximum extentallowed by law, the scope of the present invention is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

What is claimed is:
 1. A processor to execute machine-executable code,the processor comprising: a cache memory including a plurality of cachelines, each cache line including a proximity tag; and a cache controllerconfigured to: fetch first data from a first location of an informationhandling system; store the first data to a first one of the cache lines;determine first proximity information for the first data based upon thefirst location; store, in a first proximity tag associated with thefirst cache line, the first proximity information; and evict the firstcache line from the cache based upon the first proximity tag.
 2. Theprocessor of claim 1, wherein in evicting the first cache line basedupon the first proximity tag, the cache controller is further configuredto: compare the first proximity information with second proximityinformation stored in a second proximity tag associated with a secondcache line, wherein evicting the first cache line is based upon thecomparison.
 3. The processor of claim 2, wherein in evicting the firstcache line based upon the first proximity tag, the cache controller isfurther configured to: determine that second data stored in the secondcache line is from a second location that is less proximate to theprocessor than the first location based upon the comparison, whereinevicting the first cache line is further based upon the determination.4. The processor of claim 1, further comprising: a location informationregister configured to correlate a plurality of locations within a mainmemory of the information handling system with a plurality of proximityinformation; wherein in determining the first proximity information, thecache controller is further configured to: determine the first locationfrom the location information register based upon an address within themain memory associated with the first data; and select the firstproximity information from the location information register based uponthe first location.
 5. The processor of claim 4, wherein the cachecontroller is further configured to: receive the locations and theproximity information from the information handling system.
 6. Theprocessor of claim 4, wherein the cache controller is further configuredto: initiate a transaction with each of the locations; determine alatency for each transaction; determine the proximity informationassociated with each of the locations; and store the locations and theproximity information to the location information register.
 7. Theprocessor of claim 1, wherein: each cache line further includes a usagetag; and the cache controller is further configured to, before evictingthe first cache line, manipulate a first usage tag associated with thefirst cache line based upon usage of the information by the processor inaccordance with usage eviction policy, wherein evicting the first cacheline from the cache is further based upon the first usage tag.
 8. Theprocessor of claim 7, wherein in evicting the first cache line from thecache based upon the first proximity tag and the first usage tag, thecache controller if further configured to base the evicting first inorder on the first proximity tag, and second in order on the firstproximity tag.
 9. The processor of claim 7, wherein in evicting thefirst cache line from the cache based upon the first proximity tag andthe first usage tag, the cache controller if further configured to:interleave m-bits of the first proximity tag with n-bits of the firstusage tag; and determine to evict the first cache line by consideringthe m-bit of the first priority tag and the n-bits of the first usagetag in an order of the interleaving.
 10. The processor of claim 9,further comprising: a replacement tag priority register configured todefine the interleaving.
 11. A method, comprising: fetching, by a cachecontroller of a processor, first data from a first location of aninformation handling system; storing, by the cache controller, the firstdata to a first one of a plurality of cache lines of a cache of theprocessor; determining, by the cache controller, first proximityinformation for the first data based upon the first location; storing,by the cache controller, in a first proximity tag associated with thefirst cache line, the first proximity information; and evicting, by thecache controller, the first cache line from the cache based upon thefirst proximity tag.
 12. The method of claim 11, wherein in evicting thefirst cache line based upon the first proximity tag, the method furthercomprises: comparing, by the cache controller, the first proximityinformation with second proximity information stored in a secondproximity tag associated with a second cache line, wherein evicting thefirst cache line is based upon the comparison.
 13. The method of claim12, wherein in evicting the first cache line based upon the firstproximity tag, the method further comprises: determining, by the cachecontroller, that second data stored in the second cache line is from asecond location that is less proximate to the processor than the firstlocation based upon the comparison, wherein evicting the first cacheline is further based upon the determination.
 14. The method of claim11, wherein in determining the first proximity information, the cachecontroller is further configured to: determine the first location from alocation information register based upon an address within a main memoryof the information handling system, the address being associated withthe first data, wherein the location information register is configuredto correlate a plurality of locations within the main memory with aplurality of proximity information; and select the first proximityinformation from the location information register based upon the firstlocation.
 15. The method of claim 14, further comprising: receiving, bythe cache controller, the locations and the proximity information fromthe information handling system.
 16. The method of claim 14, furthercomprising: initiating, by the cache controller, a transaction with eachof the locations; determining, by the cache controller, a latency foreach transaction; determining, by the cache controller, the proximityinformation associated with each of the locations; and storing, by thecache controller, the locations and the proximity information to thelocation information register.
 17. The method of claim 11, wherein: eachcache line further includes a usage tag; and the method furthercomprises: before evicting the first cache line, manipulating, by thecache controller, a first usage tag associated with the first cache linebased upon usage of the information by the processor in accordance withusage eviction policy, wherein evicting the first cache line from thecache is further based upon the first usage tag.
 18. The method of claim17, wherein in evicting the first cache line from the cache based uponthe first proximity tag and the first usage tag, the method furthercomprises: basing, by the cache controller, the evicting first in orderon the first proximity tag, and second in order on the first proximitytag.
 19. The method of claim 17, wherein in evicting the first cacheline from the cache based upon the first proximity tag and the firstusage tag, the method further comprises: interleaving, by the cachecontroller, m-bits of the first proximity tag with n-bits of the firstusage tag; and determining, by the cache controller, to evict the firstcache line by considering the m-bit of the first priority tag and then-bits of the first usage tag in an order of the interleaving.
 20. Aninformation handling system, comprising: a main memory; and a processorincluding: a cache memory including a plurality of cache lines, eachcache line including a proximity tag; and a cache controller configuredto: fetch first data from a first location of the main memory; store thefirst data to a first one of the cache lines; determine first proximityinformation for the first data based upon the first location; store, ina first proximity tag associated with the first cache line, the firstproximity information; and evict the first cache line from the cachebased upon the first proximity tag.